About licensing

Meridian Explorer and BlueCielo Publisher usage is controlled by licenses to authorize their various features. These licenses are managed by the Meridian Enterprise license server to which Meridian Enterprise Server is configured as described in Viewing licenses and usage. The licenses and their usage can also be viewed in Meridian Enterprise Server Administration Console.

The Meridian Explorer licenses are:

• BC Explorer Server License (part number includes M--EXS). One is required for each Meridian Enterprise server that is synchronized with a Meridian Explorer repository (excluding the Meridian Enterprise Data Library).

• BC Read-Only Explorer Client License (part number includes M--EXC). One is required for every concurrent Meridian Explorer user and the license remains claimed for the duration of the browser session. The exception is mobile device users. These users must use forms authentication to view the mobile version of the Meridian Explorer website. This claims a license for each user for which forms authentication is enabled as described in Enabling forms authentication, Creating and editing groups, and Creating and editing user accounts.

• AutoVue 3D Viewer License (part number includes M--AV392). One is required for every concurrent user that uses a workstation with the 3D viewer installed. The license is claimed whether they are viewing 2D or 3D drawings.

The Publisher system link licenses are:

• BC Meridian Enterprise link (part number includes M--PUS) for publishing to or from a  Meridian Enterprise vault .

  Note    One Meridian Enterprise database connection license (Hypertrieve, SQL Server, or Oracle) is required for each Meridian Enterprise Server computer (cluster node) that publishes to or from a Meridian Enterprise vault.

• Windows file system link (part number includes FS--PUS) for publishing to or from a Windows file system.
• SharePoint system link (part number includes M--PSP) for publishing to or from a SharePoint library.
• Kronodoc system link (part number includes K--PUS) for publishing to or from a BlueCielo Project Portal or Kronodoc workspace.

All system link licenses include the use of:

• AutoVue 2D rendering module. Rendering 3D models requires an AutoVue 3D license.
• Meridian Enterprise vault extensions
• Client applications to support publishing from that system

The Publisher rendering module licenses are:

• Native Application rendering module (part number includes M--PNR) for rendering through AutoCAD, Autodesk Inventor, Microsoft Office, MicroStation, or SolidWorks.
• eSignature module (part number includes M--PES) for applying watermarks, electronic signatures, and signature pages to renditions.
• PDF Merge rendering module (part number includes M--PMD) for merging renditions into a single Adobe PDF file.

Note    When configured in a cluster, all Meridian Enterprise Server nodes (primary and secondary) require their own system link and rendering module licenses for the jobs that they process.

To obtain additional licenses, contact your BlueCielo Partner or BlueCielo ECM Solutions. For more information about registering licenses in the BlueCielo License Server, see the BlueCielo Meridian Enterprise Administrator's Guide.